feat(nextjs): Set cloudflare runtime #19084
Merged
Conversation
Contributor
node-overhead report 🧳Note: This is a synthetic benchmark with a minimal express app and does not necessarily reflect the real-world performance impact in an application.
|
Lms24
approved these changes
Jan 29, 2026
Server-side transactions are not reliably available on Cloudflare Workers, so the tests now verify the cloudflare runtime and SDK metadata using error events instead. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Contributor
Codecov Results 📊Generated by Codecov Action |
logaretm
approved these changes
Jan 30, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
We want to gain better insights how much usage we get from the SDK on Cloudflare.
When Next.js apps are deployed to Cloudflare Workers via OpenNext, the Sentry SDK now correctly reports
cloudflareas the runtime instead ofnodeorvercel-edge.e2e tests still failing cry